Build zcash on any system w/ Docker+bash via ./contrib/dev-docker/run.sh
.
#4741
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The documentation lives in
./contrib/dev/docker/README.md
.Test plan A:
zcashd
revision which has this./contrib/dev-docker
feature on a Debian/Ubuntu dev machine which also has docker installed../zcutil/build.sh
../contrib/dev-docker/run.sh
Ideally the results would be byte-wise binary compatible but that's very likely not to be the case. At the very least, both should produce all the same file names, and the full test suite should run on both, and the
zcashd --version
output of both builds should match.Test Plan B
Do the same as Test Plan A, except on the first "direct" build, do it on a system without docker, and on the second docker build, do it on a non-debian/non-ubuntu linux system with docker, then compare the results in the same manner.
What this demonstrates: This shows that building with this
dev-docker
approach allows anyone with docker to build without installing the dev toolchain directly onto their host system.